OpenEdge Development:<br />Progress Dynamics Advanced Development Other methods related to startup and shutdown

Release 10.1A: OpenEdge Development:
Progress Dynamics Advanced Development

Other methods related to startup and shutdown

The following event procedures are also related to starting up and shutting down SDOs.

destroyObject

This is the standard event procedure that runs to shut down an object. It deletes links properly and performs other cleanup tasks before deleting its own persistent procedure, as shown:
Procedure destroyObject: 
  Parameters: <none> 
  Candidate for: localization 
    If application code needs to do other work just before an object is 
destroyed, it can be done before the RUN SUPER statement in a local version 
of destroyObject. 
exitObject

For an application window to shut down properly, its objects should be deleted from the inside out. That is, the contained objects must clean up and delete themselves before the window itself is deleted. An event such as pressing a Done or Exit button inside a container can initiate this by publishing the exitObject event. The convention is that the event passes the exit request to its Container-Source. The container that can initiate the exit defines a local version and does not call the standard one.

That local exitObject is built into the SmartWindow support code, as shown:
Procedure exitObject: 
  Parameters: <none> 
  Candidate for: calling and possibly localization 
    Any button or other object inside a container that wants to close the 
container should run exitObject in its immediate container (a viewer for 
example). 
    If application code needs to do other work just before a window is 
destroyed, it can be done before the RUN SUPER statement in a local version 
of exitObject. 
launchFolderWindow

This procedure runs routinely from a dynamic browser when the user double-clicks on a row or selects the Edit or Modify button. It retrieves the value of the FolderWindowToLaunch property for the browser, which is part of the browser definition, and invokes the launchContainer procedure in the Session Manager. For more information on launchContainer and examples of its use, see Chapter 5, " Using ADM2 Properties and Methods in Progress Dynamics."

Because launchFolderWindow is specifically intended to be invoked inside a browser, you normally use the launchContainer procedure itself when you want to invoke containers from your application code.